Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6892a587a7479f8d4238eacab562f63dbd6de974be215a90f5f31c7f8dcb12bb

Tx prefix hash: 66a5e0a78f7241d3a45f5832e90330a41526f04df1062b3fd34104126eac837a
Tx public key: 87e2d983396fe9547f91d3ddc95714c5fd0d74437c286943db725a314a6268e4
Timestamp: 1736175900 Timestamp [UCT]: 2025-01-06 15:05:00 Age [y:d:h:m:s]: 00:231:05:22:11
Block: 1191544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162814 RingCT/type: yes/0
Extra: 0187e2d983396fe9547f91d3ddc95714c5fd0d74437c286943db725a314a6268e40211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c5c1be5100eb870d50f3db32a9e669b9796194ab08740216a20d75adc620d1b 0.600000000000 1678083 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": 1191554, "vin": [ { "gen": { "height": 1191544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c5c1be5100eb870d50f3db32a9e669b9796194ab08740216a20d75adc620d1b" } } ], "extra": [ 1, 135, 226, 217, 131, 57, 111, 233, 84, 127, 145, 211, 221, 201, 87, 20, 197, 253, 13, 116, 67, 124, 40, 105, 67, 219, 114, 90, 49, 74, 98, 104, 228, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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