Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c3e3921f065c3a576a1f79c79c34d1e15eb032bd8c83ed72f07ecfa6c087776

Tx prefix hash: 31c903aaf48b191b3ff4a74be509a9f984814e9cbc5f70743a4fe37dfaec08a9
Tx public key: 06f7e9aef965f5cc660fccce7472bf5457150cdf881156918574d9a9a0222ef3
Timestamp: 1727825315 Timestamp [UCT]: 2024-10-01 23:28:35 Age [y:d:h:m:s]: 00:224:01:10:25
Block: 1122438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159952 RingCT/type: yes/0
Extra: 0106f7e9aef965f5cc660fccce7472bf5457150cdf881156918574d9a9a0222ef3021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e75d834b57c13975f593df8e7f21390407e3f6ac333e0171183f3eb5dcbcf82 0.600000000000 1604871 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": 1122448, "vin": [ { "gen": { "height": 1122438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e75d834b57c13975f593df8e7f21390407e3f6ac333e0171183f3eb5dcbcf82" } } ], "extra": [ 1, 6, 247, 233, 174, 249, 101, 245, 204, 102, 15, 204, 206, 116, 114, 191, 84, 87, 21, 12, 223, 136, 17, 86, 145, 133, 116, 217, 169, 160, 34, 46, 243, 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