Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f232a5056ecf117686322743d647b2e3ac22104f4a48239255dde1753ea584d

Tx prefix hash: 61eaea705950c891f8a93c7b0242b0cc93dcb0aff859e2723d751da03472c3ff
Tx public key: 90e90594cf144a204db0340238fef4e8b79d078eaaeadfd96b394fc12fdac7bf
Timestamp: 1694776770 Timestamp [UCT]: 2023-09-15 11:19:30 Age [y:d:h:m:s]: 01:216:06:40:26
Block: 848623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415682 RingCT/type: yes/0
Extra: 0190e90594cf144a204db0340238fef4e8b79d078eaaeadfd96b394fc12fdac7bf0211000000024b8f5122000000000000000000

1 output(s) for total of 0.946585352000 dcy

stealth address amount amount idx
00: dc85d81fa6dd492aca9aace00b15f33b0bf6c68814fc5d7b82e1a290246dd0f0 0.946585352000 1302239 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": 848633, "vin": [ { "gen": { "height": 848623 } } ], "vout": [ { "amount": 946585352, "target": { "key": "dc85d81fa6dd492aca9aace00b15f33b0bf6c68814fc5d7b82e1a290246dd0f0" } } ], "extra": [ 1, 144, 233, 5, 148, 207, 20, 74, 32, 77, 176, 52, 2, 56, 254, 244, 232, 183, 157, 7, 142, 170, 234, 223, 217, 107, 57, 79, 193, 47, 218, 199, 191, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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