Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f493759d6b44d8c7a21bf9b30451780c5efba8dfc64eb3a5e67940e044f277

Tx prefix hash: 14b3444d77aaa4549130e12cd36597f1d12e5e82fae4fdca9c4dd99271b753d1
Tx public key: 0ef447544de602001670538979c891aaac8c8e8d8b12854c2f806a7fccca9463
Timestamp: 1648248281 Timestamp [UCT]: 2022-03-25 22:44:41 Age [y:d:h:m:s]: 03:220:08:14:11
Block: 466378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935388 RingCT/type: yes/0
Extra: 010ef447544de602001670538979c891aaac8c8e8d8b12854c2f806a7fccca946302110000000837cb3088000000000000000000

1 output(s) for total of 17.486236104000 dcy

stealth address amount amount idx
00: 63f0cb8bb40e9a16978d8158b5b09692b6a1407aedac73364fc3a78904d105a9 17.486236104000 884683 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": 466388, "vin": [ { "gen": { "height": 466378 } } ], "vout": [ { "amount": 17486236104, "target": { "key": "63f0cb8bb40e9a16978d8158b5b09692b6a1407aedac73364fc3a78904d105a9" } } ], "extra": [ 1, 14, 244, 71, 84, 77, 230, 2, 0, 22, 112, 83, 137, 121, 200, 145, 170, 172, 140, 142, 141, 139, 18, 133, 76, 47, 128, 106, 127, 204, 202, 148, 99, 2, 17, 0, 0, 0, 8, 55, 203, 48, 136, 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