Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b423e8741efee366bdc9ffb4512ed25d43a35d878c376818eb64bb8bca1176b5

Tx prefix hash: ddf2ed12be60f90cfb90c170c9061f6fb14bd3fc98bb7e89bdb6c6566dc99584
Tx public key: d1444ad0fbb9eeeabb8ab45e4306899b6339cbcba81f99ec257a7fe8ad2e8b2b
Timestamp: 1716917194 Timestamp [UCT]: 2024-05-28 17:26:34 Age [y:d:h:m:s]: 00:228:17:38:03
Block: 1032009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163687 RingCT/type: yes/0
Extra: 01d1444ad0fbb9eeeabb8ab45e4306899b6339cbcba81f99ec257a7fe8ad2e8b2b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcc5ebc8adaf6c4ddad8c21e3bc0938213723f0e9f83163c0a94ba6ec9d04d0d 0.600000000000 1500458 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": 1032019, "vin": [ { "gen": { "height": 1032009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcc5ebc8adaf6c4ddad8c21e3bc0938213723f0e9f83163c0a94ba6ec9d04d0d" } } ], "extra": [ 1, 209, 68, 74, 208, 251, 185, 238, 234, 187, 138, 180, 94, 67, 6, 137, 155, 99, 57, 203, 203, 168, 31, 153, 236, 37, 122, 127, 232, 173, 46, 139, 43, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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