Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28122fd3a6259d1956d93e2ecd4187fa1c9198d839dc02a3623a06413aaea166

Tx prefix hash: 038d425fa29b1279e8199cb8cdc6469b9123af1030024d0788d788f6690b6420
Tx public key: 2b424634a07107d7f02f3d1f7faea6c1c8fcc84e6effcf84321120bd3d3d5512
Timestamp: 1711076473 Timestamp [UCT]: 2024-03-22 03:01:13 Age [y:d:h:m:s]: 01:002:21:22:52
Block: 983593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263014 RingCT/type: yes/0
Extra: 012b424634a07107d7f02f3d1f7faea6c1c8fcc84e6effcf84321120bd3d3d55120211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf09045dfa8321b6d67dd5bbb3b4345eefcf46d7a33e11d0b446c491f38f1585 0.600000000000 1443734 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": 983603, "vin": [ { "gen": { "height": 983593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf09045dfa8321b6d67dd5bbb3b4345eefcf46d7a33e11d0b446c491f38f1585" } } ], "extra": [ 1, 43, 66, 70, 52, 160, 113, 7, 215, 240, 47, 61, 31, 127, 174, 166, 193, 200, 252, 200, 78, 110, 255, 207, 132, 50, 17, 32, 189, 61, 61, 85, 18, 2, 17, 0, 0, 0, 3, 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