Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3586d58417a2f1ef2c87d54f09e047310371fac1befa6a32ddc623e88474c1fb

Tx prefix hash: 0eaed301ba950df29e80732370cbebaa7593a9d393194bec5f2cdd1409ece3d2
Tx public key: e01389c9c079bd3c118d9c570d5fe4f555325b4a824e933d0c8a967eab899707
Timestamp: 1702203603 Timestamp [UCT]: 2023-12-10 10:20:03 Age [y:d:h:m:s]: 01:158:18:32:11
Block: 910016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374636 RingCT/type: yes/0
Extra: 01e01389c9c079bd3c118d9c570d5fe4f555325b4a824e933d0c8a967eab899707021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fdc4fabbfec5c50ecf645b0ad7307c5985ff16409a632596deb94fba1178ba3 0.600000000000 1367155 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": 910026, "vin": [ { "gen": { "height": 910016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fdc4fabbfec5c50ecf645b0ad7307c5985ff16409a632596deb94fba1178ba3" } } ], "extra": [ 1, 224, 19, 137, 201, 192, 121, 189, 60, 17, 141, 156, 87, 13, 95, 228, 245, 85, 50, 91, 74, 130, 78, 147, 61, 12, 138, 150, 126, 171, 137, 151, 7, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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