Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2b6172372249a014e02ddcc90d3630034a0bc53c90302c0fa7bb04ddf07b384

Tx prefix hash: 80aeb61fc12ab691b298558fbaa48150005accecf57caf10b31e1046aafe247e
Tx public key: 0c2b11327603b6131f82d7e08238838867267b9b0a2f8223d3bf24d0c9f187bf
Timestamp: 1634499018 Timestamp [UCT]: 2021-10-17 19:30:18 Age [y:d:h:m:s]: 03:072:15:45:08
Block: 355107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 829868 RingCT/type: yes/0
Extra: 010c2b11327603b6131f82d7e08238838867267b9b0a2f8223d3bf24d0c9f187bf021100000001fdc024ec000000000000000000

1 output(s) for total of 40.868012090000 dcy

stealth address amount amount idx
00: 6e5ff75bc6f1ae7aef4feaf6f1015885d00d23d82e31322df465580ae9e2e08d 40.868012090000 725111 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": 355117, "vin": [ { "gen": { "height": 355107 } } ], "vout": [ { "amount": 40868012090, "target": { "key": "6e5ff75bc6f1ae7aef4feaf6f1015885d00d23d82e31322df465580ae9e2e08d" } } ], "extra": [ 1, 12, 43, 17, 50, 118, 3, 182, 19, 31, 130, 215, 224, 130, 56, 131, 136, 103, 38, 123, 155, 10, 47, 130, 35, 211, 191, 36, 208, 201, 241, 135, 191, 2, 17, 0, 0, 0, 1, 253, 192, 36, 236, 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