Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f254885b0a36a5f9411db890f9c4e69a4c7256b6fed60160b221c1d7097d861

Tx prefix hash: 9b692bde278573b7ac46a5a1a946faa8598f6238a6915f7412ad46df7cead22f
Tx public key: bf2c40672a976e7d53e5e94b36ecc7dc29ecb3a1af177f30300ca33ecb1fe68a
Timestamp: 1719599973 Timestamp [UCT]: 2024-06-28 18:39:33 Age [y:d:h:m:s]: 00:320:06:15:45
Block: 1054229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228883 RingCT/type: yes/0
Extra: 01bf2c40672a976e7d53e5e94b36ecc7dc29ecb3a1af177f30300ca33ecb1fe68a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44056fd910afaec3269a6acafa88234da626da15794c20a011c9ea9d41cbb6ec 0.600000000000 1524590 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": 1054239, "vin": [ { "gen": { "height": 1054229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44056fd910afaec3269a6acafa88234da626da15794c20a011c9ea9d41cbb6ec" } } ], "extra": [ 1, 191, 44, 64, 103, 42, 151, 110, 125, 83, 229, 233, 75, 54, 236, 199, 220, 41, 236, 179, 161, 175, 23, 127, 48, 48, 12, 163, 62, 203, 31, 230, 138, 2, 17, 0, 0, 0, 1, 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