Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7edd9bee5030e0e6b0f34f39eb5dd4e1f01888643202ec2044d87c6850733345

Tx prefix hash: d41578b5cf62b3211a5191003e3fe9b971eba1da30a63962300d97b82bc8f26e
Tx public key: 58c51d0a8c0a039e9954751be5a0aafbc1677d4c1995475f607a9faa4781dc4a
Timestamp: 1717128309 Timestamp [UCT]: 2024-05-31 04:05:09 Age [y:d:h:m:s]: 00:322:06:09:10
Block: 1033749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230325 RingCT/type: yes/0
Extra: 0158c51d0a8c0a039e9954751be5a0aafbc1677d4c1995475f607a9faa4781dc4a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d7eace396f047dba36fd667953661a4f990b5163e0e390d3ebd09b51c1e8ec9 0.600000000000 1502220 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": 1033759, "vin": [ { "gen": { "height": 1033749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d7eace396f047dba36fd667953661a4f990b5163e0e390d3ebd09b51c1e8ec9" } } ], "extra": [ 1, 88, 197, 29, 10, 140, 10, 3, 158, 153, 84, 117, 27, 229, 160, 170, 251, 193, 103, 125, 76, 25, 149, 71, 95, 96, 122, 159, 170, 71, 129, 220, 74, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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