Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26a7dffe6dad283f47bc3bdd8f947cbdaf5d1564cef37101677dc883a31f0ef7

Tx prefix hash: 9ee9a63649d656c9c2a21add569ea7c577a1f66d2f2d2f1caca338e6f7e262c3
Tx public key: 619631ff051a30e3d9549abb07c885be03444a65304817fc466d6062be010209
Timestamp: 1704023841 Timestamp [UCT]: 2023-12-31 11:57:21 Age [y:d:h:m:s]: 01:091:22:29:21
Block: 925094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326816 RingCT/type: yes/0
Extra: 01619631ff051a30e3d9549abb07c885be03444a65304817fc466d6062be0102090211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 923fc7a9b399ca6eefc7e45b79e5da6aa0ab96f36052eb13b78f5915c1a5b4a5 0.600000000000 1382854 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": 925104, "vin": [ { "gen": { "height": 925094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "923fc7a9b399ca6eefc7e45b79e5da6aa0ab96f36052eb13b78f5915c1a5b4a5" } } ], "extra": [ 1, 97, 150, 49, 255, 5, 26, 48, 227, 217, 84, 154, 187, 7, 200, 133, 190, 3, 68, 74, 101, 48, 72, 23, 252, 70, 109, 96, 98, 190, 1, 2, 9, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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