Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 264c491f4e8fdd9635c4221397923fe81aac4032fdfc91e2f83707e0a51768c9

Tx prefix hash: 8537d39a5ed777f28f2953a884cf2b18769d321efa0497b63a8574f4c5efec1d
Tx public key: d247869bbbff8fcb4af5b85f8e67b262d91464aa4e48ae76f4f1c86ab14bd6cf
Timestamp: 1713563253 Timestamp [UCT]: 2024-04-19 21:47:33 Age [y:d:h:m:s]: 00:311:08:16:27
Block: 1004171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222566 RingCT/type: yes/0
Extra: 01d247869bbbff8fcb4af5b85f8e67b262d91464aa4e48ae76f4f1c86ab14bd6cf0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5b5efe9716dbc8ec029a9a9e333ad278d7cd2ac1081f99d2ae26cf6185b34b5 0.600000000000 1464739 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": 1004181, "vin": [ { "gen": { "height": 1004171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5b5efe9716dbc8ec029a9a9e333ad278d7cd2ac1081f99d2ae26cf6185b34b5" } } ], "extra": [ 1, 210, 71, 134, 155, 187, 255, 143, 203, 74, 245, 184, 95, 142, 103, 178, 98, 217, 20, 100, 170, 78, 72, 174, 118, 244, 241, 200, 106, 177, 75, 214, 207, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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