Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3cd36d4b02ea9aba579fc92375a8905bbec6d0dba88029878a69f896edb6345

Tx prefix hash: 94e0c3fff6f101389d6a4fe3d38ea4bc7730ab81152f2bb7c3298e91b922277b
Tx public key: 857e7fbf4faf5d2ece6613d55a576f5872f9407172d33278bbf66e6ca4a75682
Timestamp: 1738691152 Timestamp [UCT]: 2025-02-04 17:45:52 Age [y:d:h:m:s]: 00:289:23:11:49
Block: 1212078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205001 RingCT/type: yes/0
Extra: 01857e7fbf4faf5d2ece6613d55a576f5872f9407172d33278bbf66e6ca4a75682021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e00f8c60a2da3f947adcdf36268ab1c61d1037cdd92712c9dc819acdb3747f2 0.600000000000 1698845 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": 1212088, "vin": [ { "gen": { "height": 1212078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e00f8c60a2da3f947adcdf36268ab1c61d1037cdd92712c9dc819acdb3747f2" } } ], "extra": [ 1, 133, 126, 127, 191, 79, 175, 93, 46, 206, 102, 19, 213, 90, 87, 111, 88, 114, 249, 64, 113, 114, 211, 50, 120, 187, 246, 110, 108, 164, 167, 86, 130, 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