Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 359121071d7dc79fd2b65f8479d09565cf64cbccffb130952e397f3f4308d1a3

Tx prefix hash: 94e4de54759b524ff7bb7e096425b984830cb5b4debc4d74284d413d7b772601
Tx public key: fa7fb3ecb4f8f4f920cf7d47b1e87a58316a5dbfa0a760a8aa70352aed156f58
Timestamp: 1736962330 Timestamp [UCT]: 2025-01-15 17:32:10 Age [y:d:h:m:s]: 00:341:07:03:06
Block: 1198027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241481 RingCT/type: yes/0
Extra: 01fa7fb3ecb4f8f4f920cf7d47b1e87a58316a5dbfa0a760a8aa70352aed156f58021100000006d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b925c948b5014913e6e4aa5a2e3a974bd4ebd65bb575181406fcda20eefca926 0.600000000000 1684644 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": 1198037, "vin": [ { "gen": { "height": 1198027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b925c948b5014913e6e4aa5a2e3a974bd4ebd65bb575181406fcda20eefca926" } } ], "extra": [ 1, 250, 127, 179, 236, 180, 248, 244, 249, 32, 207, 125, 71, 177, 232, 122, 88, 49, 106, 93, 191, 160, 167, 96, 168, 170, 112, 53, 42, 237, 21, 111, 88, 2, 17, 0, 0, 0, 6, 216, 231, 210, 65, 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