Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6ebebe29dad033d36328575fd36a117518d2b8d7c9f913bcc20765f5101a892

Tx prefix hash: 201c1a230bab4d535c8bd26282de272d0f5afb05cc4c54b65b471ce1aa99ccda
Tx public key: f905185dda354363d5db20fe43d4258aa51977f0b4873e505b1c9d6d271ba505
Timestamp: 1711621944 Timestamp [UCT]: 2024-03-28 10:32:24 Age [y:d:h:m:s]: 00:334:18:38:35
Block: 988111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239320 RingCT/type: yes/0
Extra: 01f905185dda354363d5db20fe43d4258aa51977f0b4873e505b1c9d6d271ba50502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4163f246ad73123ba6cbc22e441f53db35bb353061ac50216fd93aa7e058e4d1 0.600000000000 1448374 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": 988121, "vin": [ { "gen": { "height": 988111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4163f246ad73123ba6cbc22e441f53db35bb353061ac50216fd93aa7e058e4d1" } } ], "extra": [ 1, 249, 5, 24, 93, 218, 53, 67, 99, 213, 219, 32, 254, 67, 212, 37, 138, 165, 25, 119, 240, 180, 135, 62, 80, 91, 28, 157, 109, 39, 27, 165, 5, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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