Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd77f25fa2ae6c35828654c537726b4900aa2227a0801024c9516d3111b0c721

Tx prefix hash: c7eb47e7fd7a0f15ac6160d9dcdf2473cbc0afd247832fd515ecb76cfe39fee2
Tx public key: f30876843df8d4a57ef621790fbd1429a7eb3299615a4da414220bc0632067f1
Timestamp: 1644429751 Timestamp [UCT]: 2022-02-09 18:02:31 Age [y:d:h:m:s]: 02:349:20:27:46
Block: 435133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769208 RingCT/type: yes/0
Extra: 01f30876843df8d4a57ef621790fbd1429a7eb3299615a4da414220bc0632067f10211000000014a0f5013000000000000000000

1 output(s) for total of 22.193410147000 dcy

stealth address amount amount idx
00: 54f17c2889f248f659415452656dc38de012bd9555e826eaeb4a7c71cae293b9 22.193410147000 846232 of 0

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": 435143, "vin": [ { "gen": { "height": 435133 } } ], "vout": [ { "amount": 22193410147, "target": { "key": "54f17c2889f248f659415452656dc38de012bd9555e826eaeb4a7c71cae293b9" } } ], "extra": [ 1, 243, 8, 118, 132, 61, 248, 212, 165, 126, 246, 33, 121, 15, 189, 20, 41, 167, 235, 50, 153, 97, 90, 77, 164, 20, 34, 11, 192, 99, 32, 103, 241, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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