Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c87f98bfd1118ce4ccca5e5b8186544ff8d1c340d113a2379fb1d9a5553ecbdd

Tx prefix hash: cfd17ab7e6c669d2de41c02d8e0f1b7bb4322dc5178b0c6047f616a3ec4b2d5f
Tx public key: e90e74ee21a90fd564a870d215bc993e70418f349a0d501df4fea2b5cc851faa
Timestamp: 1727226068 Timestamp [UCT]: 2024-09-25 01:01:08 Age [y:d:h:m:s]: 00:234:03:37:04
Block: 1117461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167189 RingCT/type: yes/0
Extra: 01e90e74ee21a90fd564a870d215bc993e70418f349a0d501df4fea2b5cc851faa021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00575b899902661f4891c02ab871dc972164fb6056ba6c1b6b994d11c10f710f 0.600000000000 1598308 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": 1117471, "vin": [ { "gen": { "height": 1117461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00575b899902661f4891c02ab871dc972164fb6056ba6c1b6b994d11c10f710f" } } ], "extra": [ 1, 233, 14, 116, 238, 33, 169, 15, 213, 100, 168, 112, 210, 21, 188, 153, 62, 112, 65, 143, 52, 154, 13, 80, 29, 244, 254, 162, 181, 204, 133, 31, 170, 2, 17, 0, 0, 0, 6, 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