Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdd1aaabee74732a7849d4c80d3a5a62ff93ff5dab94c966663eef520c82b6ba

Tx prefix hash: 8c91380ca396728ee16d953db73b5eb6937330b8109aa8b041d055b3ee9f51e6
Tx public key: e9fff69ca85558118c04198ae4d13da70b2a0d98885f584092c8a5f23cd6064f
Timestamp: 1714861812 Timestamp [UCT]: 2024-05-04 22:30:12 Age [y:d:h:m:s]: 00:332:03:08:19
Block: 1014965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237393 RingCT/type: yes/0
Extra: 01e9fff69ca85558118c04198ae4d13da70b2a0d98885f584092c8a5f23cd6064f02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ad092414254f47cc79665ca0eb2be405c8c1d9fb5e12c1c1228d42f7a056cba 0.600000000000 1478200 of 15

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": 1014975, "vin": [ { "gen": { "height": 1014965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ad092414254f47cc79665ca0eb2be405c8c1d9fb5e12c1c1228d42f7a056cba" } } ], "extra": [ 1, 233, 255, 246, 156, 168, 85, 88, 17, 140, 4, 25, 138, 228, 209, 61, 167, 11, 42, 13, 152, 136, 95, 88, 64, 146, 200, 165, 242, 60, 214, 6, 79, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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