Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2afaf0579f1d0e3585b28b1796af1d72c3d5e87a3cd39c5f642701e16256e9c9

Tx prefix hash: 6803bb7bc1d738bc1c68b449be897d331f2d55a703f33644f1618436fb500366
Tx public key: f821cfe9e74924a3b877c8b3d951809098688ae057c34539d7981c447f00e0d6
Timestamp: 1731606317 Timestamp [UCT]: 2024-11-14 17:45:17 Age [y:d:h:m:s]: 00:182:06:13:07
Block: 1153689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130095 RingCT/type: yes/0
Extra: 01f821cfe9e74924a3b877c8b3d951809098688ae057c34539d7981c447f00e0d6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28e0080295676968730d8f802513aed95e80fe11408be60e5d83c6380ff833c1 0.600000000000 1639300 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": 1153699, "vin": [ { "gen": { "height": 1153689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28e0080295676968730d8f802513aed95e80fe11408be60e5d83c6380ff833c1" } } ], "extra": [ 1, 248, 33, 207, 233, 231, 73, 36, 163, 184, 119, 200, 179, 217, 81, 128, 144, 152, 104, 138, 224, 87, 195, 69, 57, 215, 152, 28, 68, 127, 0, 224, 214, 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