Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c37ff3d67598658f0c74a94ad1df6c9c0d6bfdd45698f124f840d36fe510e2b

Tx prefix hash: 2af0b4b1cfdd632c1c468d2fed122e2a5900e659445165a8b1a2a4262c43762f
Tx public key: 9d7f4e06650249b432af10acebf56067106dfbbc2fc121f1bd226567c8689a65
Timestamp: 1735914395 Timestamp [UCT]: 2025-01-03 14:26:35 Age [y:d:h:m:s]: 00:160:00:02:02
Block: 1189371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114137 RingCT/type: yes/0
Extra: 019d7f4e06650249b432af10acebf56067106dfbbc2fc121f1bd226567c8689a65021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b431533cc2ba94239ce196ab166b3f4c8337eca5d8e7e73e2fbb8c74c7e93fd 0.600000000000 1675880 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": 1189381, "vin": [ { "gen": { "height": 1189371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b431533cc2ba94239ce196ab166b3f4c8337eca5d8e7e73e2fbb8c74c7e93fd" } } ], "extra": [ 1, 157, 127, 78, 6, 101, 2, 73, 180, 50, 175, 16, 172, 235, 245, 96, 103, 16, 109, 251, 188, 47, 193, 33, 241, 189, 34, 101, 103, 200, 104, 154, 101, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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