Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 334c084939e23236b31d8a0c46ff53cb10c1b68e875125920445569d051885b1

Tx prefix hash: 4a0934818fc2938b7937831c100fb96005fddf6897b84b8707df86f7541777d1
Tx public key: 03751989f4a9313cd2b3eae3b958c90e1e1ee08b455acf94852fe9f95c3bd8ed
Timestamp: 1738968457 Timestamp [UCT]: 2025-02-07 22:47:37 Age [y:d:h:m:s]: 00:287:01:39:04
Block: 1214382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202925 RingCT/type: yes/0
Extra: 0103751989f4a9313cd2b3eae3b958c90e1e1ee08b455acf94852fe9f95c3bd8ed021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 519c44aa7d2adb3f7c757e402787b5dbf742103a582084ad53ac15ebb095d5ea 0.600000000000 1701173 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": 1214392, "vin": [ { "gen": { "height": 1214382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "519c44aa7d2adb3f7c757e402787b5dbf742103a582084ad53ac15ebb095d5ea" } } ], "extra": [ 1, 3, 117, 25, 137, 244, 169, 49, 60, 210, 179, 234, 227, 185, 88, 201, 14, 30, 30, 224, 139, 69, 90, 207, 148, 133, 47, 233, 249, 92, 59, 216, 237, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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