Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b0b2ff05cab26ff8fd4f6be06f5fd4bef1d270d6fb1082f3995a95d67b75af0

Tx prefix hash: b9cc2e603580f0772e8b70c84276a5e91728ef2577b9d80dfa6f9cfa60d39e6f
Tx public key: 1d9c3df2be12f54d15a2c41ceaab4e1408e453f7057d67133b051905e09397d5
Timestamp: 1582511902 Timestamp [UCT]: 2020-02-24 02:38:22 Age [y:d:h:m:s]: 05:077:06:33:50
Block: 71233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1208546 RingCT/type: yes/0
Extra: 011d9c3df2be12f54d15a2c41ceaab4e1408e453f7057d67133b051905e09397d502110000000203d36d11000000000000000000

1 output(s) for total of 356.431684140000 dcy

stealth address amount amount idx
00: d73b1bb1e9b8f58f74aba8303183de2368b7112c91e1fa2cfe8eb6549df5fc51 356.431684140000 131621 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": 71243, "vin": [ { "gen": { "height": 71233 } } ], "vout": [ { "amount": 356431684140, "target": { "key": "d73b1bb1e9b8f58f74aba8303183de2368b7112c91e1fa2cfe8eb6549df5fc51" } } ], "extra": [ 1, 29, 156, 61, 242, 190, 18, 245, 77, 21, 162, 196, 28, 234, 171, 78, 20, 8, 228, 83, 247, 5, 125, 103, 19, 59, 5, 25, 5, 224, 147, 151, 213, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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