Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96c9d94498f5ddbb51d5b5cddf7a3505eebc735c240308788e042b23ec06c59f

Tx prefix hash: f357055a0098f863a703c9cbabfbd5e46b89bc65d07c397f85d4af4b83658a7f
Tx public key: 64f457b0f8ad9141954d9c2d8db104206f29757e3d8905d4dcf40e01ffcc8c2c
Timestamp: 1695478993 Timestamp [UCT]: 2023-09-23 14:23:13 Age [y:d:h:m:s]: 01:249:13:14:34
Block: 854464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439464 RingCT/type: yes/0
Extra: 0164f457b0f8ad9141954d9c2d8db104206f29757e3d8905d4dcf40e01ffcc8c2c02110000000e33af99f4000000000000000000

1 output(s) for total of 0.905328335000 dcy

stealth address amount amount idx
00: 44ec187dbf74c8639bd912c308d023042a19e99fe569993c35f6cbf31e3c9a4a 0.905328335000 1308438 of 0

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": 854474, "vin": [ { "gen": { "height": 854464 } } ], "vout": [ { "amount": 905328335, "target": { "key": "44ec187dbf74c8639bd912c308d023042a19e99fe569993c35f6cbf31e3c9a4a" } } ], "extra": [ 1, 100, 244, 87, 176, 248, 173, 145, 65, 149, 77, 156, 45, 141, 177, 4, 32, 111, 41, 117, 126, 61, 137, 5, 212, 220, 244, 14, 1, 255, 204, 140, 44, 2, 17, 0, 0, 0, 14, 51, 175, 153, 244, 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