Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09739f00ed3cf084a44976a232000c4ca5bbd5e7cdff7c52c1a546a7b303df64

Tx prefix hash: 0fbd81ee25d5b16b48042fc39f927d560a13eca3649fd301cc50d506ebd55c16
Tx public key: 62976c7f851e8b5d5477dd065a9d0875d464173eed20e1eca8b7cca17782a83a
Timestamp: 1644786380 Timestamp [UCT]: 2022-02-13 21:06:20 Age [y:d:h:m:s]: 03:097:05:12:22
Block: 437971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 849481 RingCT/type: yes/0
Extra: 0162976c7f851e8b5d5477dd065a9d0875d464173eed20e1eca8b7cca17782a83a0211000000025eb576c5000000000000000000

1 output(s) for total of 21.718036715000 dcy

stealth address amount amount idx
00: 9bfbf5848e57220dc5462520fe09a461e2f299d2ded38df2f02535cb8e0fce5d 21.718036715000 849738 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": 437981, "vin": [ { "gen": { "height": 437971 } } ], "vout": [ { "amount": 21718036715, "target": { "key": "9bfbf5848e57220dc5462520fe09a461e2f299d2ded38df2f02535cb8e0fce5d" } } ], "extra": [ 1, 98, 151, 108, 127, 133, 30, 139, 93, 84, 119, 221, 6, 90, 157, 8, 117, 212, 100, 23, 62, 237, 32, 225, 236, 168, 183, 204, 161, 119, 130, 168, 58, 2, 17, 0, 0, 0, 2, 94, 181, 118, 197, 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