Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66d125b0b62f8537d92a6cae9e9fe51c76df31de6277d30d6d3d041848d1417a

Tx prefix hash: 5a7f8ea85ce17559c322b9f4460ce751f81cff4550a9046b16d12acf9c5904d8
Tx public key: fd41d5c91289b29945a45ebc5d3072bf8ab0057549bc92104787988932e24394
Timestamp: 1577666636 Timestamp [UCT]: 2019-12-30 00:43:56 Age [y:d:h:m:s]: 04:332:10:38:57
Block: 34659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126707 RingCT/type: yes/0
Extra: 01fd41d5c91289b29945a45ebc5d3072bf8ab0057549bc92104787988932e243940211000000064ac5aa02000000000000000000

1 output(s) for total of 471.152175556000 dcy

stealth address amount amount idx
00: 98de124861fdda96b1935660d9d53e4b00b2df509a12e2042602eb2f45f53d3b 471.152175556000 58367 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": 34669, "vin": [ { "gen": { "height": 34659 } } ], "vout": [ { "amount": 471152175556, "target": { "key": "98de124861fdda96b1935660d9d53e4b00b2df509a12e2042602eb2f45f53d3b" } } ], "extra": [ 1, 253, 65, 213, 201, 18, 137, 178, 153, 69, 164, 94, 188, 93, 48, 114, 191, 138, 176, 5, 117, 73, 188, 146, 16, 71, 135, 152, 137, 50, 226, 67, 148, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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