Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab70525cf0c49dc2b60acba4749d3916011ca950a708a6bc35b3cb74ecd4aadf

Tx prefix hash: 4ebe71566a0034d5c4b783bea94c198ad8512a6e51ffc2f30910fefb97a5387e
Tx public key: e31501b0687d27883e4b50e4ef2c3e3f83a1cebf0630b7b43befc0d7c8623b75
Timestamp: 1735795998 Timestamp [UCT]: 2025-01-02 05:33:18 Age [y:d:h:m:s]: 00:099:03:09:59
Block: 1188377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70644 RingCT/type: yes/0
Extra: 01e31501b0687d27883e4b50e4ef2c3e3f83a1cebf0630b7b43befc0d7c8623b750211000000062609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cafdada53b7ce9e659de7e5b177d9cdb08cd69355a0f5020366036a7ab38c83d 0.600000000000 1674878 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": 1188387, "vin": [ { "gen": { "height": 1188377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cafdada53b7ce9e659de7e5b177d9cdb08cd69355a0f5020366036a7ab38c83d" } } ], "extra": [ 1, 227, 21, 1, 176, 104, 125, 39, 136, 62, 75, 80, 228, 239, 44, 62, 63, 131, 161, 206, 191, 6, 48, 183, 180, 59, 239, 192, 215, 200, 98, 59, 117, 2, 17, 0, 0, 0, 6, 38, 9, 179, 160, 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