Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 686f07b3b8fa31a8f55e5942433193eac5dd93284c1e4fd2957a6953aa18e9a3

Tx prefix hash: 15b99a1255207b75b65436f0d069ba98fd721e5aa6f5303d39bc372cce0d0469
Tx public key: 10b2bca231c3dfa8d3673d6651d5cacf8c0ab9993f271c99201c9d16c2d117e8
Timestamp: 1657685469 Timestamp [UCT]: 2022-07-13 04:11:09 Age [y:d:h:m:s]: 02:177:00:05:20
Block: 542641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 647857 RingCT/type: yes/0
Extra: 0110b2bca231c3dfa8d3673d6651d5cacf8c0ab9993f271c99201c9d16c2d117e8021100000018cb8520c2000000000000000000

1 output(s) for total of 9.772490323000 dcy

stealth address amount amount idx
00: 97c64407f6d4ea66f26a54e1f8ed53602eb1f22c0387124bb89becb7e8a195bc 9.772490323000 973224 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": 542651, "vin": [ { "gen": { "height": 542641 } } ], "vout": [ { "amount": 9772490323, "target": { "key": "97c64407f6d4ea66f26a54e1f8ed53602eb1f22c0387124bb89becb7e8a195bc" } } ], "extra": [ 1, 16, 178, 188, 162, 49, 195, 223, 168, 211, 103, 61, 102, 81, 213, 202, 207, 140, 10, 185, 153, 63, 39, 28, 153, 32, 28, 157, 22, 194, 209, 23, 232, 2, 17, 0, 0, 0, 24, 203, 133, 32, 194, 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