Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a70ae4a8becca1403a82673bdfc5b787635758c31936980360b7b87eb808892c

Tx prefix hash: cc8288964e546fab831998058c5a039baeeb0fe7e0aa2368c6b7259a4f1f0a8c
Tx public key: a09bb1b66a026a81bb45380f49cda6a6de2f7fe2e5fc0f85a580de64926aacd7
Timestamp: 1714612798 Timestamp [UCT]: 2024-05-02 01:19:58 Age [y:d:h:m:s]: 00:335:18:10:57
Block: 1012893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240002 RingCT/type: yes/0
Extra: 01a09bb1b66a026a81bb45380f49cda6a6de2f7fe2e5fc0f85a580de64926aacd70211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c461ccfd8a267c63600c97e228efd7becf349706fabd4fe01b9f7e1cc736c386 0.600000000000 1475554 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": 1012903, "vin": [ { "gen": { "height": 1012893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c461ccfd8a267c63600c97e228efd7becf349706fabd4fe01b9f7e1cc736c386" } } ], "extra": [ 1, 160, 155, 177, 182, 106, 2, 106, 129, 187, 69, 56, 15, 73, 205, 166, 166, 222, 47, 127, 226, 229, 252, 15, 133, 165, 128, 222, 100, 146, 106, 172, 215, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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