Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 355c5ad2a2d9f9a83469a92bb5cafb2a9f4edb9fb3d5d281a69f8c7166c10ac9

Tx prefix hash: 137c50a7836fc893a810c95f0af78764648f18a8a5fd7c041351864b7bc51864
Tx public key: f072267d00df6f2140365336e2bcd59e9e207450fc7773e34ea3ef9ee535aeac
Timestamp: 1732694127 Timestamp [UCT]: 2024-11-27 07:55:27 Age [y:d:h:m:s]: 00:201:22:55:39
Block: 1162705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144079 RingCT/type: yes/0
Extra: 01f072267d00df6f2140365336e2bcd59e9e207450fc7773e34ea3ef9ee535aeac021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2d83c0cd37e0d6ca3a4839db87e68ef4ab169e517561f0df9e68d84fc15094c 0.600000000000 1648362 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": 1162715, "vin": [ { "gen": { "height": 1162705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2d83c0cd37e0d6ca3a4839db87e68ef4ab169e517561f0df9e68d84fc15094c" } } ], "extra": [ 1, 240, 114, 38, 125, 0, 223, 111, 33, 64, 54, 83, 54, 226, 188, 213, 158, 158, 32, 116, 80, 252, 119, 115, 227, 78, 163, 239, 158, 229, 53, 174, 172, 2, 17, 0, 0, 0, 1, 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