Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ec34f5083c162f84431f354172e5be97717fdb3379fec73a1bb771e1bde760f

Tx prefix hash: fe1c4a43964d70594dfbb5fefdacdb9597ca8dffc18a5e5aaa093be5339d164c
Tx public key: e08a15e215efe1cc4987d75213e5f95163c2e13e490610b86495e4b00b1d7ff0
Timestamp: 1714938474 Timestamp [UCT]: 2024-05-05 19:47:54 Age [y:d:h:m:s]: 00:341:12:18:34
Block: 1015601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244116 RingCT/type: yes/0
Extra: 01e08a15e215efe1cc4987d75213e5f95163c2e13e490610b86495e4b00b1d7ff00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fff1daf81c771ad1a5e93dc07d0f95bf8809594721b3968bd5ee0cd2c2b8c598 0.600000000000 1479012 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": 1015611, "vin": [ { "gen": { "height": 1015601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fff1daf81c771ad1a5e93dc07d0f95bf8809594721b3968bd5ee0cd2c2b8c598" } } ], "extra": [ 1, 224, 138, 21, 226, 21, 239, 225, 204, 73, 135, 215, 82, 19, 229, 249, 81, 99, 194, 225, 62, 73, 6, 16, 184, 100, 149, 228, 176, 11, 29, 127, 240, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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