Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e80f03e4f7dc1f5e5dccb34ee761740542d8f5ddc9fe824d13cb9d666f4e2a

Tx prefix hash: 7d4ac356955ff6100d3379d95a1357dc00e5c4bbad18180a41026000cd5cf77b
Tx public key: 555635c4f9287b59249ce731f306920595f503cc34f784a031d24b68a87c6499
Timestamp: 1726523374 Timestamp [UCT]: 2024-09-16 21:49:34 Age [y:d:h:m:s]: 00:052:05:43:03
Block: 1111641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 37335 RingCT/type: yes/0
Extra: 01555635c4f9287b59249ce731f306920595f503cc34f784a031d24b68a87c64990208dcec7e7af9173697

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d995cf4d68dc54b02c5c112cb2c7decc4a5c007012d98fcf763564b5b1adb364 0.600000000000 1590670 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": 1111651, "vin": [ { "gen": { "height": 1111641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d995cf4d68dc54b02c5c112cb2c7decc4a5c007012d98fcf763564b5b1adb364" } } ], "extra": [ 1, 85, 86, 53, 196, 249, 40, 123, 89, 36, 156, 231, 49, 243, 6, 146, 5, 149, 245, 3, 204, 52, 247, 132, 160, 49, 210, 75, 104, 168, 124, 100, 153, 2, 8, 220, 236, 126, 122, 249, 23, 54, 151 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8