Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7565ed40b073dcde358e69fce6c59eea9863ac5d1564bfdbb7bbfa296c36e39a

Tx prefix hash: 1e6d91df1136e0f2fc14d843008c2553e32104e2cdf2d039a021979ad40d8f42
Tx public key: fa63c2415ec3fead9db933fc28a4e10d9f5eb0f49d73d4b51af5f6605db6db81
Timestamp: 1735218883 Timestamp [UCT]: 2024-12-26 13:14:43 Age [y:d:h:m:s]: 00:102:12:04:11
Block: 1183641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72997 RingCT/type: yes/0
Extra: 01fa63c2415ec3fead9db933fc28a4e10d9f5eb0f49d73d4b51af5f6605db6db81021100000019007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ba7ed333dc9fb135603b0b1bd675862ba878db69a1f27230ee27719ccccfe6d 0.600000000000 1670088 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": 1183651, "vin": [ { "gen": { "height": 1183641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ba7ed333dc9fb135603b0b1bd675862ba878db69a1f27230ee27719ccccfe6d" } } ], "extra": [ 1, 250, 99, 194, 65, 94, 195, 254, 173, 157, 185, 51, 252, 40, 164, 225, 13, 159, 94, 176, 244, 157, 115, 212, 181, 26, 245, 246, 96, 93, 182, 219, 129, 2, 17, 0, 0, 0, 25, 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