Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbbc8006148daaf6fbcb9833d3a698de959e3e84219cf7e278e0723b6cfc7f35

Tx prefix hash: 80ef5931c1e6c6b16461b86d077b51aee3835e902d8f80aaa5fd3159f61ddbcf
Tx public key: 9b069129d7ede54f3f3c27fe0587e073641424b0522b53d9e55e5df4f0e9a8cf
Timestamp: 1696726756 Timestamp [UCT]: 2023-10-08 00:59:16 Age [y:d:h:m:s]: 01:254:05:57:52
Block: 864814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442678 RingCT/type: yes/0
Extra: 019b069129d7ede54f3f3c27fe0587e073641424b0522b53d9e55e5df4f0e9a8cf021100000001bfa22221000000000000000000

1 output(s) for total of 0.836589196000 dcy

stealth address amount amount idx
00: 66d8417c1ef309d317d7d3c1b26871fb7f8a880bee74fab30fbe6bc46a5f3d97 0.836589196000 1319334 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": 864824, "vin": [ { "gen": { "height": 864814 } } ], "vout": [ { "amount": 836589196, "target": { "key": "66d8417c1ef309d317d7d3c1b26871fb7f8a880bee74fab30fbe6bc46a5f3d97" } } ], "extra": [ 1, 155, 6, 145, 41, 215, 237, 229, 79, 63, 60, 39, 254, 5, 135, 224, 115, 100, 20, 36, 176, 82, 43, 83, 217, 229, 94, 93, 244, 240, 233, 168, 207, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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