Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3460d7cd960d0da111e71f33a0772505f6af33db8cfc947d090172bf4c268e7e

Tx prefix hash: fc3c4730c03e69740ea374bcc53cf743a2f63abff2ca4cae2bb01863c27a61d3
Tx public key: 68bfb747176f4ef9b9b6689e2a5b79da335068b0b340b85b7e9372addc3da165
Timestamp: 1701168425 Timestamp [UCT]: 2023-11-28 10:47:05 Age [y:d:h:m:s]: 01:339:23:39:26
Block: 901429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501863 RingCT/type: yes/0
Extra: 0168bfb747176f4ef9b9b6689e2a5b79da335068b0b340b85b7e9372addc3da16502110000000475e3f0e9000000000000000000

1 output(s) for total of 0.632690777000 dcy

stealth address amount amount idx
00: a91bc13164c1cea60d433d019376db42751d5db540473ca2586e899c7ceb2473 0.632690777000 1357992 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": 901439, "vin": [ { "gen": { "height": 901429 } } ], "vout": [ { "amount": 632690777, "target": { "key": "a91bc13164c1cea60d433d019376db42751d5db540473ca2586e899c7ceb2473" } } ], "extra": [ 1, 104, 191, 183, 71, 23, 111, 78, 249, 185, 182, 104, 158, 42, 91, 121, 218, 51, 80, 104, 176, 179, 64, 184, 91, 126, 147, 114, 173, 220, 61, 161, 101, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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