Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90665f7371214e7b39ed41c0dfaf5c7634ad7cdb08dd64fc4a37446d7daf3c2a

Tx prefix hash: f03d1c79fedf2200307d4541b1ef1d65dd7d1ca7b32e0f66453b4b7161a60805
Tx public key: ea4595e4a976c878c3dad4cf88379070e34a06bcda042fc6b4d518e7924de566
Timestamp: 1725392083 Timestamp [UCT]: 2024-09-03 19:34:43 Age [y:d:h:m:s]: 00:202:02:05:30
Block: 1102263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144259 RingCT/type: yes/0
Extra: 01ea4595e4a976c878c3dad4cf88379070e34a06bcda042fc6b4d518e7924de566021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a7bd1b27b555078af07239f1de9edf48a89aa0ac5e28a35137c5d16d1ca0ee4 0.600000000000 1578630 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": 1102273, "vin": [ { "gen": { "height": 1102263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a7bd1b27b555078af07239f1de9edf48a89aa0ac5e28a35137c5d16d1ca0ee4" } } ], "extra": [ 1, 234, 69, 149, 228, 169, 118, 200, 120, 195, 218, 212, 207, 136, 55, 144, 112, 227, 74, 6, 188, 218, 4, 47, 198, 180, 213, 24, 231, 146, 77, 229, 102, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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