Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed7a4745f266da506f6a5cc496b07f46009f27604c675c49e39e967d73cb4fc2

Tx prefix hash: bd2cc47056b755cc2664f4a2f48f6247c0807209e404633995ccc16b18fadfa3
Tx public key: 22ce2a59a3d40f541fd074245c0d6e1840caf401f99998fa378b192b297ccf72
Timestamp: 1735997946 Timestamp [UCT]: 2025-01-04 13:39:06 Age [y:d:h:m:s]: 00:300:00:55:17
Block: 1190061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211930 RingCT/type: yes/0
Extra: 0122ce2a59a3d40f541fd074245c0d6e1840caf401f99998fa378b192b297ccf72021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5510ce265b4cc451dfdcb1df5c9c79b8e02cf5e4ff67ca1dc7590f3ffc379ea4 0.600000000000 1676576 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": 1190071, "vin": [ { "gen": { "height": 1190061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5510ce265b4cc451dfdcb1df5c9c79b8e02cf5e4ff67ca1dc7590f3ffc379ea4" } } ], "extra": [ 1, 34, 206, 42, 89, 163, 212, 15, 84, 31, 208, 116, 36, 92, 13, 110, 24, 64, 202, 244, 1, 249, 153, 152, 250, 55, 139, 25, 43, 41, 124, 207, 114, 2, 17, 0, 0, 0, 4, 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