Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46a723b2fa17209abe8be7503cee49fa40d6ebbf71a63c5509a686ae2f67ad4a

Tx prefix hash: c14fdbae8da54f74242be062d74425f140693ac97332005204eb66089f244def
Tx public key: 55b3d51f9bd73442ccff1da7e8389e392404c2b5b8f68448f0bc9b7908ad1df9
Timestamp: 1742187512 Timestamp [UCT]: 2025-03-17 04:58:32 Age [y:d:h:m:s]: 00:293:20:35:08
Block: 1241041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207816 RingCT/type: yes/0
Extra: 0155b3d51f9bd73442ccff1da7e8389e392404c2b5b8f68448f0bc9b7908ad1df9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c3a4962f0af99939809eb217b2f35e91fb07f08c8fddf9c6f5279d6f801dfef 0.600000000000 1728014 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": 1241051, "vin": [ { "gen": { "height": 1241041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c3a4962f0af99939809eb217b2f35e91fb07f08c8fddf9c6f5279d6f801dfef" } } ], "extra": [ 1, 85, 179, 213, 31, 155, 215, 52, 66, 204, 255, 29, 167, 232, 56, 158, 57, 36, 4, 194, 181, 184, 246, 132, 72, 240, 188, 155, 121, 8, 173, 29, 249, 2, 17, 0, 0, 0, 4, 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