Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b9baa4cc31ceea6b3d329b6253408b473a3aac31de52f05a172c5a66ad82725

Tx prefix hash: 26f081beeea0b81cf2f09ac9bf26dbe4d0f99e6b189df748f93987898086474c
Tx public key: 0ad3edb6b6bb598330faa05250b22fef67b5dc860d9cdca83c6e866d42240b9f
Timestamp: 1713770159 Timestamp [UCT]: 2024-04-22 07:15:59 Age [y:d:h:m:s]: 00:360:21:54:40
Block: 1005904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258015 RingCT/type: yes/0
Extra: 010ad3edb6b6bb598330faa05250b22fef67b5dc860d9cdca83c6e866d42240b9f02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b80a4e1ca1fa08fde02f63cdb3bb52d2297bb3e7991c5c65c925e2a3c9995055 0.600000000000 1466746 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": 1005914, "vin": [ { "gen": { "height": 1005904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b80a4e1ca1fa08fde02f63cdb3bb52d2297bb3e7991c5c65c925e2a3c9995055" } } ], "extra": [ 1, 10, 211, 237, 182, 182, 187, 89, 131, 48, 250, 160, 82, 80, 178, 47, 239, 103, 181, 220, 134, 13, 156, 220, 168, 60, 110, 134, 109, 66, 36, 11, 159, 2, 17, 0, 0, 0, 5, 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