Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0e6eacc9fb3ede4f69d5675f1c45f201133d45fc2a308663f223a6d3b00dce

Tx prefix hash: 7e52eb0c9c422624271719258d6dc5059645e4594381b4c14a0a7e86d0d40e2f
Tx public key: b329cf16400325897e5e42e9961427c68b5db6227e3ee24185b39ed4537e4728
Timestamp: 1735978275 Timestamp [UCT]: 2025-01-04 08:11:15 Age [y:d:h:m:s]: 00:161:05:08:31
Block: 1189898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114965 RingCT/type: yes/0
Extra: 01b329cf16400325897e5e42e9961427c68b5db6227e3ee24185b39ed4537e472802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c782ee2052e38262ea0f5ab806e99a62bf5940a6b7bb6ec4c1281b919297a11d 0.600000000000 1676413 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": 1189908, "vin": [ { "gen": { "height": 1189898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c782ee2052e38262ea0f5ab806e99a62bf5940a6b7bb6ec4c1281b919297a11d" } } ], "extra": [ 1, 179, 41, 207, 22, 64, 3, 37, 137, 126, 94, 66, 233, 150, 20, 39, 198, 139, 93, 182, 34, 126, 62, 226, 65, 133, 179, 158, 212, 83, 126, 71, 40, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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