Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aedce4805d92eba8afd101359a2c410ce20307d6d6283fac9eb5f622a3fd200

Tx prefix hash: 497240638f761b07cac9693dced48eebc0b942638f2862071c2f727a53cc1ea2
Tx public key: aaa83fe72f8056f3c857dcfee44781074bd7233454dc2fbee52f1e38741ab0f6
Timestamp: 1671439274 Timestamp [UCT]: 2022-12-19 08:41:14 Age [y:d:h:m:s]: 02:113:23:55:20
Block: 655855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 603164 RingCT/type: yes/0
Extra: 01aaa83fe72f8056f3c857dcfee44781074bd7233454dc2fbee52f1e38741ab0f60211000000047e406890000000000000000000

1 output(s) for total of 4.119837673000 dcy

stealth address amount amount idx
00: c7a9b589e1e39972f4c3864662d28e5b6f9b76fe92d48d1c0d2751f905000ef4 4.119837673000 1096432 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": 655865, "vin": [ { "gen": { "height": 655855 } } ], "vout": [ { "amount": 4119837673, "target": { "key": "c7a9b589e1e39972f4c3864662d28e5b6f9b76fe92d48d1c0d2751f905000ef4" } } ], "extra": [ 1, 170, 168, 63, 231, 47, 128, 86, 243, 200, 87, 220, 254, 228, 71, 129, 7, 75, 215, 35, 52, 84, 220, 47, 190, 229, 47, 30, 56, 116, 26, 176, 246, 2, 17, 0, 0, 0, 4, 126, 64, 104, 144, 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