Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ff8f0d2441d3376cf853e41ebcaceeba63895084aba17949d751196e6ef7da

Tx prefix hash: 053cb37e8ad02c4f6f9fa0c8d4c42876c2ee9a57462d2682caf60dfe945f6e78
Tx public key: 40aec704b43ddd81f89c7d6af37e8f7272b42eafc6f918defa74f49e77708cf4
Timestamp: 1582234136 Timestamp [UCT]: 2020-02-20 21:28:56 Age [y:d:h:m:s]: 05:258:10:40:11
Block: 68972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1335690 RingCT/type: yes/0
Extra: 0140aec704b43ddd81f89c7d6af37e8f7272b42eafc6f918defa74f49e77708cf40211000000074943cd9f000000000000000000

1 output(s) for total of 362.633513284000 dcy

stealth address amount amount idx
00: c7558241a999d8db8f3054bb63a5b05daecb78a5da59db5d3aa4a2e41f8a26fb 362.633513284000 127219 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": 68982, "vin": [ { "gen": { "height": 68972 } } ], "vout": [ { "amount": 362633513284, "target": { "key": "c7558241a999d8db8f3054bb63a5b05daecb78a5da59db5d3aa4a2e41f8a26fb" } } ], "extra": [ 1, 64, 174, 199, 4, 180, 61, 221, 129, 248, 156, 125, 106, 243, 126, 143, 114, 114, 180, 46, 175, 198, 249, 24, 222, 250, 116, 244, 158, 119, 112, 140, 244, 2, 17, 0, 0, 0, 7, 73, 67, 205, 159, 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