Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf424459a2dace809e87f044a845432e4a19bd9cfe6830534cf9460b2e97a64f

Tx prefix hash: 93da751dcc643840e8624ca58a28f5b7fc9414fe97e5b66b61381f9ee644199f
Tx public key: 67c87e675411ebfd1abeb146640d6ad78faea5e101204ff8b57e9ec9cc5f2b7f
Timestamp: 1745202710 Timestamp [UCT]: 2025-04-21 02:31:50 Age [y:d:h:m:s]: 00:192:13:23:52
Block: 1265966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135344 RingCT/type: yes/0
Extra: 0167c87e675411ebfd1abeb146640d6ad78faea5e101204ff8b57e9ec9cc5f2b7f02110000000c6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29f56988bba0c9a4cee87e924294dd609c79be41f047e86e4a5b5b1120a4b845 0.600000000000 1753179 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": 1265976, "vin": [ { "gen": { "height": 1265966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29f56988bba0c9a4cee87e924294dd609c79be41f047e86e4a5b5b1120a4b845" } } ], "extra": [ 1, 103, 200, 126, 103, 84, 17, 235, 253, 26, 190, 177, 70, 100, 13, 106, 215, 143, 174, 165, 225, 1, 32, 79, 248, 181, 126, 158, 201, 204, 95, 43, 127, 2, 17, 0, 0, 0, 12, 108, 152, 170, 61, 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