Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f59906209ed414168eb5a1c12d7b4b57e1b4a25438c9ff31364d8f6a2d9fab1f

Tx prefix hash: 7adadb6d7f925c839c857656db14dba5c637ab9208041a2f10ad80d7158951bb
Tx public key: bc914cc125d9c4b8c4caad4ff773b8056d6121d962458a0d2826dce0d6281cb4
Timestamp: 1709398491 Timestamp [UCT]: 2024-03-02 16:54:51 Age [y:d:h:m:s]: 01:033:02:40:45
Block: 969668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284663 RingCT/type: yes/0
Extra: 01bc914cc125d9c4b8c4caad4ff773b8056d6121d962458a0d2826dce0d6281cb40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70eabe1a0a567fb3cc532d4816bf5ac6bd94ce02fb4efcf4a4f8776b2bbed40f 0.600000000000 1429505 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": 969678, "vin": [ { "gen": { "height": 969668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70eabe1a0a567fb3cc532d4816bf5ac6bd94ce02fb4efcf4a4f8776b2bbed40f" } } ], "extra": [ 1, 188, 145, 76, 193, 37, 217, 196, 184, 196, 202, 173, 79, 247, 115, 184, 5, 109, 97, 33, 217, 98, 69, 138, 13, 40, 38, 220, 224, 214, 40, 28, 180, 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