Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd330539f4d855af44018f3ef91b65a5cdbfb0e03837849e9f9d7166e7330bb6

Tx prefix hash: 28867158884c9685a01500c572eae0fae9e82b12d1dc35d08714651dd953d13b
Tx public key: e12e2b3a429d917ca1e3630153b5c5931969bab7881a7577c1aea44364790604
Timestamp: 1706175269 Timestamp [UCT]: 2024-01-25 09:34:29 Age [y:d:h:m:s]: 01:073:12:20:27
Block: 942918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313617 RingCT/type: yes/0
Extra: 01e12e2b3a429d917ca1e3630153b5c5931969bab7881a7577c1aea4436479060402110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d677bdee49039b22fdb0184f226b6b5a4b7caa803a0b6b7a692cf68b2d79383 0.600000000000 1401098 of 15

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": 942928, "vin": [ { "gen": { "height": 942918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d677bdee49039b22fdb0184f226b6b5a4b7caa803a0b6b7a692cf68b2d79383" } } ], "extra": [ 1, 225, 46, 43, 58, 66, 157, 145, 124, 161, 227, 99, 1, 83, 181, 197, 147, 25, 105, 186, 183, 136, 26, 117, 119, 193, 174, 164, 67, 100, 121, 6, 4, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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