Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 691f6747cbb853c5624c42e76d7943372af8c485c96593d48cda1de017a9ce00

Tx prefix hash: 44037633e585e09acd37da61c8a2514dc9d0d43f9773530ca6d9fddfd2b9558f
Tx public key: f1d9729e2e6546bbf82daa91dbbf10d88ee10a3e70b5906f6aeb90e1fa02cca1
Timestamp: 1726870383 Timestamp [UCT]: 2024-09-20 22:13:03 Age [y:d:h:m:s]: 00:220:20:48:40
Block: 1114514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157694 RingCT/type: yes/0
Extra: 01f1d9729e2e6546bbf82daa91dbbf10d88ee10a3e70b5906f6aeb90e1fa02cca1021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 312adc895a496846a5a9d24dffb2e32af6b58b7ddbdc5f19238881a59b4675dc 0.600000000000 1594315 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": 1114524, "vin": [ { "gen": { "height": 1114514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "312adc895a496846a5a9d24dffb2e32af6b58b7ddbdc5f19238881a59b4675dc" } } ], "extra": [ 1, 241, 217, 114, 158, 46, 101, 70, 187, 248, 45, 170, 145, 219, 191, 16, 216, 142, 225, 10, 62, 112, 181, 144, 111, 106, 235, 144, 225, 250, 2, 204, 161, 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