Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f8e5918cf29123b1ab20422b2701f0ca10f895fbaded5647dafa4c1896048f8

Tx prefix hash: d55a376998e10ddc2c062449b8a30dc9f45c7b249388086402851a3197a98f69
Tx public key: b9cb8e61c38e60413c94bfb21a866918d0191eef29b293bc3f9da075aaea2f02
Timestamp: 1720792321 Timestamp [UCT]: 2024-07-12 13:52:01 Age [y:d:h:m:s]: 00:104:00:30:49
Block: 1064131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74468 RingCT/type: yes/0
Extra: 01b9cb8e61c38e60413c94bfb21a866918d0191eef29b293bc3f9da075aaea2f0202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ed0d89bdc08191a26203cc0cd75db096bc45d0545ae16af8210d61f88b27106 0.600000000000 1534654 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": 1064141, "vin": [ { "gen": { "height": 1064131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ed0d89bdc08191a26203cc0cd75db096bc45d0545ae16af8210d61f88b27106" } } ], "extra": [ 1, 185, 203, 142, 97, 195, 142, 96, 65, 60, 148, 191, 178, 26, 134, 105, 24, 208, 25, 30, 239, 41, 178, 147, 188, 63, 157, 160, 117, 170, 234, 47, 2, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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