Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d40e6fa670a5c8ded37b0fab31d2c469414ac1bb1108fce6e92e949e188e67b

Tx prefix hash: 4725afd619b5202e4d8ee6ff68ad57ed5d32a9811076d8f55af5ce98429c81d7
Tx public key: 1b69b57919727f183cb1b11a0e67be27aa592d253cdaa22028e4171bd2bfb18b
Timestamp: 1702543822 Timestamp [UCT]: 2023-12-14 08:50:22 Age [y:d:h:m:s]: 01:032:18:28:44
Block: 912829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284778 RingCT/type: yes/0
Extra: 011b69b57919727f183cb1b11a0e67be27aa592d253cdaa22028e4171bd2bfb18b02110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55d41f6569cb6d7ce339f237954fcb0448ac25c9651a7e8743a1a5d4f000d800 0.600000000000 1370065 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": 912839, "vin": [ { "gen": { "height": 912829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55d41f6569cb6d7ce339f237954fcb0448ac25c9651a7e8743a1a5d4f000d800" } } ], "extra": [ 1, 27, 105, 181, 121, 25, 114, 127, 24, 60, 177, 177, 26, 14, 103, 190, 39, 170, 89, 45, 37, 60, 218, 162, 32, 40, 228, 23, 27, 210, 191, 177, 139, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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