Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e929b5136f9ed17471c8b19af259bcf394d52dc85e255d4daa60b7b6155e2101

Tx prefix hash: 1d488c764fbb8c45edea054bc6e06b749e66b9dd39516e8d7fbc4e910c3e215e
Tx public key: 2df3d0da645fca61e743978dc2f63b14bed1570504d358e56e2a4096a66fabc8
Timestamp: 1730909670 Timestamp [UCT]: 2024-11-06 16:14:30 Age [y:d:h:m:s]: 00:134:05:44:54
Block: 1147915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95780 RingCT/type: yes/0
Extra: 012df3d0da645fca61e743978dc2f63b14bed1570504d358e56e2a4096a66fabc8021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42b4bb60ee0efe772fb0621c7293f95fd7aeba4db84661fb096dbd23ace6f50e 0.600000000000 1632628 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": 1147925, "vin": [ { "gen": { "height": 1147915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42b4bb60ee0efe772fb0621c7293f95fd7aeba4db84661fb096dbd23ace6f50e" } } ], "extra": [ 1, 45, 243, 208, 218, 100, 95, 202, 97, 231, 67, 151, 141, 194, 246, 59, 20, 190, 209, 87, 5, 4, 211, 88, 229, 110, 42, 64, 150, 166, 111, 171, 200, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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