Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0edc0c057754bb7fddea4d5964b4f633d7c9c46673114bacbb99d4cf731dfbb0

Tx prefix hash: f16e55bcb06c701ad2687863c8b823bea64621981ceced850cb4f494dd18da84
Tx public key: a1d2d235ee56569ef2e8a81a9a3695735a43c8e17d644e5cd486d936bce2ac75
Timestamp: 1721673310 Timestamp [UCT]: 2024-07-22 18:35:10 Age [y:d:h:m:s]: 00:296:14:27:45
Block: 1071413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211940 RingCT/type: yes/0
Extra: 01a1d2d235ee56569ef2e8a81a9a3695735a43c8e17d644e5cd486d936bce2ac7502110000000391e13c04000000000000000000

1 output(s) for total of 0.615570000000 dcy

stealth address amount amount idx
00: 5e230d9fa8850febf05c2122aa7572d6a5f21d8c1f3b9f056a1547a396c4843a 0.615570000000 1543634 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": 1071423, "vin": [ { "gen": { "height": 1071413 } } ], "vout": [ { "amount": 615570000, "target": { "key": "5e230d9fa8850febf05c2122aa7572d6a5f21d8c1f3b9f056a1547a396c4843a" } } ], "extra": [ 1, 161, 210, 210, 53, 238, 86, 86, 158, 242, 232, 168, 26, 154, 54, 149, 115, 90, 67, 200, 225, 125, 100, 78, 92, 212, 134, 217, 54, 188, 226, 172, 117, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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