Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfda80c465226bf63ca46c5a8809ce551610b9bf3e4a695f51b3a1c9df4f6957

Tx prefix hash: f831be446d65c083cea22e5a6372397df759e160fab0327cff25073142776f6c
Tx public key: 714c91c232810dfb36f99d1e1d7b95a4d1d571da6ffddf5f18522424b763dcf1
Timestamp: 1697031824 Timestamp [UCT]: 2023-10-11 13:43:44 Age [y:d:h:m:s]: 01:224:16:23:24
Block: 867350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421649 RingCT/type: yes/0
Extra: 01714c91c232810dfb36f99d1e1d7b95a4d1d571da6ffddf5f18522424b763dcf10211000000064b8f5122000000000000000000

1 output(s) for total of 0.820558270000 dcy

stealth address amount amount idx
00: d5b821dc02899d2eec60dcb1bc5dc34f2f2d41f314c4fe47bbe5512a8c4c90d4 0.820558270000 1322026 of 0

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": 867360, "vin": [ { "gen": { "height": 867350 } } ], "vout": [ { "amount": 820558270, "target": { "key": "d5b821dc02899d2eec60dcb1bc5dc34f2f2d41f314c4fe47bbe5512a8c4c90d4" } } ], "extra": [ 1, 113, 76, 145, 194, 50, 129, 13, 251, 54, 249, 157, 30, 29, 123, 149, 164, 209, 213, 113, 218, 111, 253, 223, 95, 24, 82, 36, 36, 183, 99, 220, 241, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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