Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fc24337d83877ca9669a6786f546d76a72dd14bee582f636d8a23c04cd5670e

Tx prefix hash: 90ecaa256bedf67967e585798cd66e71097a18ef7f3166c3b95b1f21d8be09cc
Tx public key: 3fcf865308aefab0400fa3d0afd7e3c03a7af0bb211b01ae6a5a6645091a48ac
Timestamp: 1673157926 Timestamp [UCT]: 2023-01-08 06:05:26 Age [y:d:h:m:s]: 02:305:04:52:16
Block: 670064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737533 RingCT/type: yes/0
Extra: 013fcf865308aefab0400fa3d0afd7e3c03a7af0bb211b01ae6a5a6645091a48ac02110000000575e3f0e9000000000000000000

1 output(s) for total of 3.696577096000 dcy

stealth address amount amount idx
00: e02dbcd56afaae62188fd75edcb72e1afc6ab0d80d75fb9843863633a0a494bb 3.696577096000 1111437 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": 670074, "vin": [ { "gen": { "height": 670064 } } ], "vout": [ { "amount": 3696577096, "target": { "key": "e02dbcd56afaae62188fd75edcb72e1afc6ab0d80d75fb9843863633a0a494bb" } } ], "extra": [ 1, 63, 207, 134, 83, 8, 174, 250, 176, 64, 15, 163, 208, 175, 215, 227, 192, 58, 122, 240, 187, 33, 27, 1, 174, 106, 90, 102, 69, 9, 26, 72, 172, 2, 17, 0, 0, 0, 5, 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