Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46de6885fa344770e61fdd2d6be2db23cc1af18ca6aa2150f48d21f27b430a27

Tx prefix hash: 4487c1e52754b84db8fea0e04f141fae2ca76f072369a49111c1468d69c2c0cf
Tx public key: d8d0f9b4fe9249385afb0b26c7290600e65b1c97bb4156c91f43b1a13caae4a4
Timestamp: 1715121086 Timestamp [UCT]: 2024-05-07 22:31:26 Age [y:d:h:m:s]: 00:136:16:13:31
Block: 1017107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97905 RingCT/type: yes/0
Extra: 01d8d0f9b4fe9249385afb0b26c7290600e65b1c97bb4156c91f43b1a13caae4a402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1049172fb017225364ad82b50610f22fa93e985b7e2352f2e041263105f49b01 0.600000000000 1480874 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": 1017117, "vin": [ { "gen": { "height": 1017107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1049172fb017225364ad82b50610f22fa93e985b7e2352f2e041263105f49b01" } } ], "extra": [ 1, 216, 208, 249, 180, 254, 146, 73, 56, 90, 251, 11, 38, 199, 41, 6, 0, 230, 91, 28, 151, 187, 65, 86, 201, 31, 67, 177, 161, 60, 170, 228, 164, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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