Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58330578eb8443d3553f9a2bc874fb5712e2c23d6b94e679fab4cfbdbf6ac743

Tx prefix hash: 8e3e3520b07724dd1b880ba565bd3ed1358b89d43f3d981fb4db46e74ca51b1f
Tx public key: a66b659d04a86d96502e2e8c7485d67c12db0fe24c9fd74b7c04f3a80d4f2597
Timestamp: 1582003201 Timestamp [UCT]: 2020-02-18 05:20:01 Age [y:d:h:m:s]: 05:016:02:51:50
Block: 67257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164569 RingCT/type: yes/0
Extra: 01a66b659d04a86d96502e2e8c7485d67c12db0fe24c9fd74b7c04f3a80d4f25970211000000064ac5aa02000000000000000000

1 output(s) for total of 367.409555369000 dcy

stealth address amount amount idx
00: 80e7a3a975cf6defedcefc8056bb6f3f2c259a7b3d6e7401978795e7dcbcbfa1 367.409555369000 123920 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": 67267, "vin": [ { "gen": { "height": 67257 } } ], "vout": [ { "amount": 367409555369, "target": { "key": "80e7a3a975cf6defedcefc8056bb6f3f2c259a7b3d6e7401978795e7dcbcbfa1" } } ], "extra": [ 1, 166, 107, 101, 157, 4, 168, 109, 150, 80, 46, 46, 140, 116, 133, 214, 124, 18, 219, 15, 226, 76, 159, 215, 75, 124, 4, 243, 168, 13, 79, 37, 151, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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