Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c1c2ce74922c0e10205f0d45e6a758d699108b41dcaf6d621eaf2c7b1af979b

Tx prefix hash: 94e758664cfb9cab88a214b982ae2bac260dd2533bfb0e71cbe21170f3ead90e
Tx public key: 25023ebce20e833a1ad5fc0ede0b3811846161ed127224244c4ec3f9a79c88ec
Timestamp: 1675043056 Timestamp [UCT]: 2023-01-30 01:44:16 Age [y:d:h:m:s]: 01:348:02:15:33
Block: 685735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509746 RingCT/type: yes/0
Extra: 0125023ebce20e833a1ad5fc0ede0b3811846161ed127224244c4ec3f9a79c88ec021100000002835e4d22000000000000000000

1 output(s) for total of 3.280090372000 dcy

stealth address amount amount idx
00: 3fbc0cc333da1b7491f49779d654a07838529eaf3c2e0476a4c7552fac8b2a0f 3.280090372000 1128112 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": 685745, "vin": [ { "gen": { "height": 685735 } } ], "vout": [ { "amount": 3280090372, "target": { "key": "3fbc0cc333da1b7491f49779d654a07838529eaf3c2e0476a4c7552fac8b2a0f" } } ], "extra": [ 1, 37, 2, 62, 188, 226, 14, 131, 58, 26, 213, 252, 14, 222, 11, 56, 17, 132, 97, 97, 237, 18, 114, 36, 36, 76, 78, 195, 249, 167, 156, 136, 236, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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