Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eec58a133396681f757eec711a09d8d38ecf22b7bba7fc5b20921ecc20c6c2c2

Tx prefix hash: 349880fe29d55599eb0b7b4d6b2b8af4f5aebd22f13655ffb1de31f8ea017c5d
Tx public key: 561608eae878a2f9577a7fc23a35c51eb3d267ef0b76054a8b3319c00343764d
Timestamp: 1718567428 Timestamp [UCT]: 2024-06-16 19:50:28 Age [y:d:h:m:s]: 00:277:21:12:51
Block: 1045694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198558 RingCT/type: yes/0
Extra: 01561608eae878a2f9577a7fc23a35c51eb3d267ef0b76054a8b3319c00343764d02110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 716830a13946a010de262f44e718acf769924b402a8672c089455a6f935ef702 0.600000000000 1515333 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": 1045704, "vin": [ { "gen": { "height": 1045694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "716830a13946a010de262f44e718acf769924b402a8672c089455a6f935ef702" } } ], "extra": [ 1, 86, 22, 8, 234, 232, 120, 162, 249, 87, 122, 127, 194, 58, 53, 197, 30, 179, 210, 103, 239, 11, 118, 5, 74, 139, 51, 25, 192, 3, 67, 118, 77, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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