Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9abfd39a1e13210ffbc1203833e1aa9ec8e84460cf5dc2a8ce7db4466d5b143

Tx prefix hash: 973b570646e93e3891c758bf1d4e22dae9c2b16601c420925662ad5205e05c96
Tx public key: 0c589c8692fec9e3396511489af23b6b55f25f7a1917aefa2bdd220c85caad6a
Timestamp: 1714897448 Timestamp [UCT]: 2024-05-05 08:24:08 Age [y:d:h:m:s]: 00:248:05:21:15
Block: 1015255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177661 RingCT/type: yes/0
Extra: 010c589c8692fec9e3396511489af23b6b55f25f7a1917aefa2bdd220c85caad6a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d62e3cb423b54ecac70e5d37da8ada1f2790c9e9207573f7972d1728d6a757aa 0.600000000000 1478570 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": 1015265, "vin": [ { "gen": { "height": 1015255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d62e3cb423b54ecac70e5d37da8ada1f2790c9e9207573f7972d1728d6a757aa" } } ], "extra": [ 1, 12, 88, 156, 134, 146, 254, 201, 227, 57, 101, 17, 72, 154, 242, 59, 107, 85, 242, 95, 122, 25, 23, 174, 250, 43, 221, 34, 12, 133, 202, 173, 106, 2, 17, 0, 0, 0, 1, 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