Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38f25cec46d728b9e1146467c06885fac4c6e09a105170c48a146057dc214d0e

Tx prefix hash: 47d017a410af504be2737e46bee16d116faf093c80d72aa6b5d76a772cb89213
Tx public key: 3aa521f2877bc3b95860b29c03d961579de961f5cdb91d599be48d3037b53340
Timestamp: 1716323268 Timestamp [UCT]: 2024-05-21 20:27:48 Age [y:d:h:m:s]: 00:236:22:01:55
Block: 1027075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169561 RingCT/type: yes/0
Extra: 013aa521f2877bc3b95860b29c03d961579de961f5cdb91d599be48d3037b533400211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d98fe96b9a78a67058d1ed14b9cfa4e8809ca93c7653bf93e5eee3272c2bf577 0.600000000000 1494510 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": 1027085, "vin": [ { "gen": { "height": 1027075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d98fe96b9a78a67058d1ed14b9cfa4e8809ca93c7653bf93e5eee3272c2bf577" } } ], "extra": [ 1, 58, 165, 33, 242, 135, 123, 195, 185, 88, 96, 178, 156, 3, 217, 97, 87, 157, 233, 97, 245, 205, 185, 29, 89, 155, 228, 141, 48, 55, 181, 51, 64, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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