Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2091a5a7c81c9ff71d06b1141880e2880ff02edc5a258deff9c39d466a77b2c1

Tx prefix hash: f92bbd3d313eb791153ea7f3cb2de8b2f2d96db7de3a13580691333c4d082d23
Tx public key: 809769ac394d09ede7c00e8af8da3e83018e5dd71b5aa1f05ef18c7200169c3f
Timestamp: 1724214193 Timestamp [UCT]: 2024-08-21 04:23:13 Age [y:d:h:m:s]: 01:079:14:33:18
Block: 1092502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315337 RingCT/type: yes/0
Extra: 01809769ac394d09ede7c00e8af8da3e83018e5dd71b5aa1f05ef18c7200169c3f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3dd650ff81711866bd2fff739d3a54efdba7537ec0ce7d98c8612e05e0e7756 0.600000000000 1567261 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": 1092512, "vin": [ { "gen": { "height": 1092502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3dd650ff81711866bd2fff739d3a54efdba7537ec0ce7d98c8612e05e0e7756" } } ], "extra": [ 1, 128, 151, 105, 172, 57, 77, 9, 237, 231, 192, 14, 138, 248, 218, 62, 131, 1, 142, 93, 215, 27, 90, 161, 240, 94, 241, 140, 114, 0, 22, 156, 63, 2, 17, 0, 0, 0, 2, 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