Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e86dd44dc2b7e2e74617e9b1ad0475d66aaa12554383c6d6a78f147fec899fef

Tx prefix hash: 3aed4d7b7dd63e94a09682f85bc6b36100038f971ea2b3bd210e4fa10a57279d
Tx public key: 339b5415f2b967800864549da41744c77ae4c8449b1903f021b754929ecf14ce
Timestamp: 1698603443 Timestamp [UCT]: 2023-10-29 18:17:23 Age [y:d:h:m:s]: 01:187:23:16:09
Block: 880386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395349 RingCT/type: yes/0
Extra: 01339b5415f2b967800864549da41744c77ae4c8449b1903f021b754929ecf14ce021100000004faf35c9c000000000000000000

1 output(s) for total of 0.742874975000 dcy

stealth address amount amount idx
00: 9fce2d4da7c49137d65a4f226061ce265df4bb5e3f397be0bdc426f7c3b1a052 0.742874975000 1335942 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": 880396, "vin": [ { "gen": { "height": 880386 } } ], "vout": [ { "amount": 742874975, "target": { "key": "9fce2d4da7c49137d65a4f226061ce265df4bb5e3f397be0bdc426f7c3b1a052" } } ], "extra": [ 1, 51, 155, 84, 21, 242, 185, 103, 128, 8, 100, 84, 157, 164, 23, 68, 199, 122, 228, 200, 68, 155, 25, 3, 240, 33, 183, 84, 146, 158, 207, 20, 206, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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