Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 111a9527008f214eaeb3541b5afc9eb030c258471631a8b9f3c026dfc36fe0af

Tx prefix hash: 041f2bbaf73e5a652a1c447238d93016c55090a6bba38a14b794bd972eaab0a1
Tx public key: fb7e912682c1f30dcb8bbdbdbefb33977df8313416375c1d0b8ee80976ea9637
Timestamp: 1719131937 Timestamp [UCT]: 2024-06-23 08:38:57 Age [y:d:h:m:s]: 01:142:00:36:16
Block: 1050345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360065 RingCT/type: yes/0
Extra: 01fb7e912682c1f30dcb8bbdbdbefb33977df8313416375c1d0b8ee80976ea96370211000000090fbbc4c5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d22396fe9e942e4ccb287f9fa010b8518bd185357835ebe4eec34910d48bc6f0 0.600000000000 1520510 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": 1050355, "vin": [ { "gen": { "height": 1050345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d22396fe9e942e4ccb287f9fa010b8518bd185357835ebe4eec34910d48bc6f0" } } ], "extra": [ 1, 251, 126, 145, 38, 130, 193, 243, 13, 203, 139, 189, 189, 190, 251, 51, 151, 125, 248, 49, 52, 22, 55, 92, 29, 11, 142, 232, 9, 118, 234, 150, 55, 2, 17, 0, 0, 0, 9, 15, 187, 196, 197, 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