Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 79cf075104e9a97dad1082c42a9b9867898f148e63364a2b2578e176b48a4877

Tx prefix hash: 0623fe627e2a83b25ba0fc1a949e469351ffe92fbafa0cab1733bc70ce7ff284
Tx public key: 24d0d8e9a1d5e5b463ba5f44151493e4dd5e7f802c804a854da4a9eb31724836
Timestamp: 1719521543 Timestamp [UCT]: 2024-06-27 20:52:23 Age [y:d:h:m:s]: 00:178:09:31:41
Block: 1053579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127708 RingCT/type: yes/0
Extra: 0124d0d8e9a1d5e5b463ba5f44151493e4dd5e7f802c804a854da4a9eb317248360211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1408f546f4de37780c55bc388d2077fbb584d95306c0f8ec73f64bc2da6a29b6 0.600000000000 1523926 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1053589, "vin": [ { "gen": { "height": 1053579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1408f546f4de37780c55bc388d2077fbb584d95306c0f8ec73f64bc2da6a29b6" } } ], "extra": [ 1, 36, 208, 216, 233, 161, 213, 229, 180, 99, 186, 95, 68, 21, 20, 147, 228, 221, 94, 127, 128, 44, 128, 74, 133, 77, 164, 169, 235, 49, 114, 72, 54, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8