Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eca4c8e88fe05b3d290b803b9227789b7c54ca0645dcd29aea5b50981955285e

Tx prefix hash: bd2bf0ceae20e7d5f5c87070c9dc07a551f167e2a11814d4b21bf577ae4da0fe
Tx public key: c32ead5626d2da73731b9e465c0a771c3866952b63e0e22f4f4436f472171da3
Timestamp: 1706849129 Timestamp [UCT]: 2024-02-02 04:45:29 Age [y:d:h:m:s]: 01:068:01:25:45
Block: 948522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309706 RingCT/type: yes/0
Extra: 01c32ead5626d2da73731b9e465c0a771c3866952b63e0e22f4f4436f472171da302110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5442d19d0e12eeb2788a38e699b3c38b493602cc77f55ede6c7f5e36449ee085 0.600000000000 1406946 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": 948532, "vin": [ { "gen": { "height": 948522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5442d19d0e12eeb2788a38e699b3c38b493602cc77f55ede6c7f5e36449ee085" } } ], "extra": [ 1, 195, 46, 173, 86, 38, 210, 218, 115, 115, 27, 158, 70, 92, 10, 119, 28, 56, 102, 149, 43, 99, 224, 226, 47, 79, 68, 54, 244, 114, 23, 29, 163, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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