Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca54f8206d7993a492a8bdc473670884211f939859427fb99a8e8e37e2ff83cf

Tx prefix hash: ed05bef88df4409bbdf560b183ae86543fa3c99e4faf488dd66cc068ffc3b6b2
Tx public key: 74b6a8781fce9eced1fef67a7d75e23eaa3d9bc4182643742863f97ce8a19dc8
Timestamp: 1739616460 Timestamp [UCT]: 2025-02-15 10:47:40 Age [y:d:h:m:s]: 00:234:20:47:09
Block: 1219717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165583 RingCT/type: yes/0
Extra: 0174b6a8781fce9eced1fef67a7d75e23eaa3d9bc4182643742863f97ce8a19dc80211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f11ae2650b4c82659eeb1e1f61d8c1bef97c8577985dbb13513ff4247032748 0.600000000000 1706548 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": 1219727, "vin": [ { "gen": { "height": 1219717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f11ae2650b4c82659eeb1e1f61d8c1bef97c8577985dbb13513ff4247032748" } } ], "extra": [ 1, 116, 182, 168, 120, 31, 206, 158, 206, 209, 254, 246, 122, 125, 117, 226, 62, 170, 61, 155, 196, 24, 38, 67, 116, 40, 99, 249, 124, 232, 161, 157, 200, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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