Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b67569d85e30ba0f19335b9d8db552f31982b33724822f67623c5e42066a2c0a

Tx prefix hash: c959b6df9008d9008ba3492908904ee7f2af4609c910edf2a9c7980d8522fc67
Tx public key: 8757f6f32332c4a2f5a47e87f78c8af2f3c77b93cfd94d5d1d86f1cb89f8ef2c
Timestamp: 1716450626 Timestamp [UCT]: 2024-05-23 07:50:26 Age [y:d:h:m:s]: 00:321:00:33:55
Block: 1028135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229444 RingCT/type: yes/0
Extra: 018757f6f32332c4a2f5a47e87f78c8af2f3c77b93cfd94d5d1d86f1cb89f8ef2c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d107659b4dc1d2d9e018545902d8794d24aa697e29a244175926d99c9a88998 0.600000000000 1496072 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": 1028145, "vin": [ { "gen": { "height": 1028135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d107659b4dc1d2d9e018545902d8794d24aa697e29a244175926d99c9a88998" } } ], "extra": [ 1, 135, 87, 246, 243, 35, 50, 196, 162, 245, 164, 126, 135, 247, 140, 138, 242, 243, 199, 123, 147, 207, 217, 77, 93, 29, 134, 241, 203, 137, 248, 239, 44, 2, 17, 0, 0, 0, 3, 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