Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5fd2f5adac8d58ea114a433beaa14e609764ac904a3406e96ee87690a7c5164

Tx prefix hash: a7ee91ba9575e9222cdcec354cb62c9a08f9d7a9cffbe2f5b8834aa0702a1255
Tx public key: 1a48d1a48070666f89bd373485d06efacf19a132c2a42272e6bf17d119c86156
Timestamp: 1672591533 Timestamp [UCT]: 2023-01-01 16:45:33 Age [y:d:h:m:s]: 01:336:01:57:07
Block: 665380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501225 RingCT/type: yes/0
Extra: 011a48d1a48070666f89bd373485d06efacf19a132c2a42272e6bf17d119c8615602110000000c33af99f4000000000000000000

1 output(s) for total of 3.831067568000 dcy

stealth address amount amount idx
00: 07ae460f1a361b74675f471258d90c3ba1c727e510d585698d4396299a0cce9e 3.831067568000 1106421 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": 665390, "vin": [ { "gen": { "height": 665380 } } ], "vout": [ { "amount": 3831067568, "target": { "key": "07ae460f1a361b74675f471258d90c3ba1c727e510d585698d4396299a0cce9e" } } ], "extra": [ 1, 26, 72, 209, 164, 128, 112, 102, 111, 137, 189, 55, 52, 133, 208, 110, 250, 207, 25, 161, 50, 194, 164, 34, 114, 230, 191, 23, 209, 25, 200, 97, 86, 2, 17, 0, 0, 0, 12, 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